Power Tools 1993 November

home *** CD-ROM | disk | FTP | other *** search

/ Power Tools 1993 November - Disc 2 / Power Tools Plus (Disc 2 of 2)(November 1993)(HP).iso / hotlines / wsyhl / domig / domig.txt < prev next >

Wrap

Text File | 1993-03-03 | 19KB | 404 lines

Slide 1 Nomen 1 Introduction HP Domain to HPUX Migration Seminar Slide 2 Migration Planning Overview Nomen 10 These are the areas I will be covering, beginning with a discussion of the preliminary steps you should consider prior to migration planning. This information is based on the Domain to HP-UX Interoper- ability Planning Guide and the Lab notes, included in your handouts Slide 3 Preliminary Steps Nomen 12 These steps will help determine your overall project objectives and to assess the impact of differences between Domain and HP-UX functionality. This will allow you to focus on the critical few areas that will make your migration a success. Slide 4 Software Planning Nomen 13 Your understanding of Softare planning is critical. The basic assumption is that there will be a period of time you will want to interoperate between Domain and HP-UX. We will spend some time addressing interoperability and migration in each of these areas beginning with Operating Systems. Slide 5 Operating Systems Nomen 14 Make them aware that they are moving from a peer to peer world to a client server oriented world in HP-UX and that impact has on all areas Ask how much Knowledge thay have of Unix OS systems Customers whose production environments require the use of Domain should move to 10.4 and start utilizing the standards included in this release. This will make moving to HP-UX much easier in the future. In the optimal migration plan, your OS strategy goal should be to get to 10.4 for Domain and HP-UX 9.0. Slide 6 System Administration Nomen 15 We will cover the following areas and I will give you some tips in each area from the experiences we have gained in other companies migrate Slide 7 User Environment Nomen 17 The user environment, if planned correctly, can minimize the learning curve for your users. X11R4 is available today on 10.3.5 and you should start using this now to save user startup time in moving to HP-UX, use X Apollo if you are still on SR 10.3.5 Migrate to HPVUE when you get to SR 10.4 Utilize HP-VUE as a common user front end across both OS environments, set up action definitions and file types using pull down menus, dialogue boxes and icons. DMX incorporates most of the DM editor using Motif. DMX won't work with Domain G* R based applications Tech TIP: Discuss on-line documentation, man pages vs. /com/ help and discuss manuals on CD-ROM Slide 8 Shell Scripts Nomen 18 Domain Aegis and HP-UX commands are substantially different requiring re-write of some shell scripts. The POSIX Shell specifications are being finalized and will ensure maximum portability. The existing korn shell closely matches the POSIX specifications and can be used today on both HP-UX and Domain for immediate portability. Sun doesn't include a korn shell in their environment. Tech TIP: Interworks is building a simple scanning tool to assist customers in porting Aegis scripts. In the mean time, consult Interworks references and white papers for user experiences Slide 9 Printing Nomen 19 Emphasis should be on the ability for printing to Domain from HP-UX Print services between HP-UX and Domain require TCP/IP com- munications to be established between all servers and clients For BSD print services, maintain printcap files on all clients and servers HP's SAM admin tool greatly simplifies the configuration of printers on the HP-UX side In the Lab notes section of your materials are detailed instructions for setting up printing Slide 10 Back Up/Recovery Nomen 20 Each OS includes proprietary backup utilities and are unsuit- able for heterogeneous networks. Cpio and tar are UNIX utilities common to both and better used in small installa- tions to minimize admin time Tech TIP: If your network has existing wbak archives we recommend you maintain a Domain node in the network as an rbak server for those archives Slide 11 Back Up/Recovery Nomen 21 Omnibak is the recommended solution for mixed environments Omnibak is a file system that allows you to recover either complete files or individual files In addition to Domain and HP-UX, Omnibak will support Sun/ Sparc systems at the next release Tech TIP: Special low cost evaluation copies are available for you to test Omnibak in your network. Contact your local HP sales rep. Slide 12 Electronic Mail Nomen 22 The Berkeley mail dispatch service, Sendmail provides the recommended basis for mail interoperability HP's version of Elm is supported under HP-UX VUE and the public domain version for Apollo systems is widely available through many Internet archive servers TechTIP: Map user names in the sendmail aliases file to mask users from the user@hostname reeequirement of sendmail.. Work with Mentor Graphics on integration of Mentor Mail Slide 13 Software Installation/Update Nomen 23 No interoperability or migration functions are offered between HP-UX and Domain systems, but, the Release install (RAI) tools from Domain and the /etc/update tools in HP-UX have some functionality in common. Tech TIP: Set up a netdistd server to better manage the install process of OS and layered products. The RMFN tool is a great tool to help manage disk space. Slide 14 Tools/Products Nomen 24 Spend some time explaining these commands These are the key HP-UX commands to become familiar with. HP's SAM product automates a number of these commands for the user Tech TIP: Be aware that UNIX does not dynamically allocate Swap space - it must be set. Learn how to check for kernel parameters and how to set them up for tuning. This is a major departure from Domain Slide 15 Tools/Products Nomen 25 Here are a number of HP-UX supported tools for you to better understand how you can maximize performance on an HP-UX system. Glance plus is an on-line monitoring and diagnostic tool that provides performance and OS parameters. Slide 16 Software Planning Place Holder Nomen 26 After looking at a system view, let's now look at the Networking aspects of migration. Slide 17 Networking Nomen 27 These are the areas we will focus on Slide 18 TCP/IP Nomen 28 ARPA services and TCP/IP are integral parts of both the HP-UX and Domain operating systems. These protocols and services provide standards based communications interoperability between HP-UX and Domain systems as well as those of other manufacturers. On Domain, TCP/IP functionality is optional and must be enabled for an individual node. On HP-UX, TCP/IP is resident in the kernel and is thus available on all systems. Tech TIP: Use NIS for host name resolution since BIND requires configuration of name servers, not a trivial task. This is an area to get training if you are not comfortable - it is critical to understand TCP/IP to make your hetero- geneous network go smoothly. Slide 19 File Access Nomen 29 The Domain file system provides a peer to peer file sharing architecture in which all systems with disks can be treated as equals and files are usually distributed widely among the nodes in the workgroup. The Domain file system is non- standard and is not supported on HP-UX. NFS provides a more client-server oriented architecture in which a given workstation tends to access a few server nodes for most of its file sharing needs. Moving towards a client-server architecture will have implications on your network topology, system administration and daily operations. Tech TIP: Set up simple naming and mounting scheme. Utilize UNIX model for file and directory permissions. Slide 20 File Access Nomen 30 We discourage customers from mounting the Domain network root(//) Performance in this configuration is poor because each access requires both an NFS and a Domain OS operation. Install NFS on every Domain node whether client or server. Maximize the number of deamons for the performance of the file access times Servers should be placed to minimize the number of network hops to a clients. Otherwise gateways will become bottle- necks and limit NFS performance. Slide 21 Network Login Nomen 31 The NIS component of NFS 4.1 can be used to import or export information from the Domain registry to a heterogeneous network of Domain and HP-UX machines. In order to make NFS 4.1 widely implemented, Domain NFS maintenance customers will automatically receive NFS 4.1. Slide 22 Network Login Nomen 32 This slide contains a few more key Tech TIP's for file system access. Slide 23 Tools and Products Nomen 33 Here is a llisting of the more common HP-UX network diagnostic tools. We reommend training to better understand each of these tools. Slide 24 Tools/Products Nomen 34 Network Node Manager is an application available on HP-UX only, but it can monitor any workstation connected on the LAN or WAN, Domain or HP-UX provided the workstation is running under the SNMP user agent software. Any Domain system running SR10.3 or later includes the SNMP user software. Emphasize the reference material that contains more detail Slide 25 Software Planning Nomen 35 The next area to consider in Software planning is the impact of migration on your own in-house software Slide 26 Porting In House Applications Nomen 36 Let's look at these areas Slide 27 Moving to Standards Nomen 37 With the release of Domain SR 10.4 users have access to a very rich set of industry standards. You can immediately begin porting software applications from Domain proprietary system calls to industry standard calls. Applications ported or developed under SR10.4 will port to HP-UX with a minimum effort. Tech TIP: When standards based software is available on many different platforms, you can choose among performance and features when deciding which workstations to buy for your production environment. Slide 28 Graphics Nomen 38 Graphics is one of the more common areas you will have to port To port Domain code to standard code you will have to change Domain GPR graphics to X and Motif calls. Tech TIP: To help in this area, the ADVISE tools include source code to a set of sample GPR to X programs written in C. These samples can be used to emulate many of the GPR calls while the application code is being ported. Slide 29 Programmers Environment Nomen 39 Check to see if any DSEE users are in the Audience before delving too deeply into this area HP is committed to offering, on HP-UX, functionality equival- ent to the DSEE users have enjoyed over the years. HP intends to make a transition from DSEE to this new technology as easy as possible for DSEE users. After an evaluation based on input from our DSEE customers HP has determined that ClearCasse from Atria Software offers all that DSEE functionality. HP and Atria have signed an agreement under shich HP will distribute and support the ClearCase product. There are also alternative to ClearCase available as you can see. The plans for DSEE have not changed. There are no plans for major enhancements to DSEE. DSEE maintenance customers will continue to receive bug-fixes. Slide 30 Tools/Documentation Nomen 40 Slide 31 Hardware Planning Nomen 45 In this section we will look at ways you can move from your existing workstations as well as provide information on peripherals and network hardware. Slide 32 Workstation Upgrade Paths Nomen 46 Your choice of upgrade path depends on such factors as your specific starting point, your near term need for better performance, and you operational timing requirements. You can upgrade from any point to the HP-UX workstation with either a box swap or PA-RISC board upgrade. HP offers a unique path for series 400 customers to swap their current CPU boar for a PA-RISC board that will result in at least a 450% increase in system performance. HP emphasaizes the Series 700 HP-UX/Domain intereoperability because these systems not only give you significant added performance but will place you directly on our strategic hardware development path. Slide 33 433/425 Peripheral Support Table Nomen 47 As you migrate consideration must be given to support for peripherals, such as disk, tape drives, and hardcopy devices. This table is a simplified version for the systems that can be upgraded by a board swap. There is much more detailed information contained in you handout material. It is important to note that Domain ISA cards such as the PC coprocessor, serial controller AT, parallel interface card, and SPE card are not supported in HP-UX systems. Slide 34 Supported Network Physical Layers Nomen 48 Ask what type of physical network the audience has currently Existing Domain workstations are typically connected via Apollo Token Ring, ethernet, or IBM Token Ring. Series 700 workstations support built in 802.3 that provides thick, thin, or twisted pair standard ethernet connectivity The recommended physical layer option for Domain/HP-UX interoperability is Ethernet. Slide 35 Network Examples Nomen 49 Slide 36 Nomen 50 Spend some time on these slides reviewing the setup and possible pitfalls of alternates like gateways, routers, subnets, etc. The following show examples of possible network configurations supporting interoperability between Domain/OS and HP-UX. In 3-7, using an DN node for a router will not provide the performance needed. The series 700 has proven to be a very acceptable option. Slide 37 Hardware Planning Summary Nomen 51 Extensive information is provided in you material to allow you to assess your hardware requirements. As a result of extensive feedback from the Domain base HP has created a PA-RISC board upgrade path to the Series 700. We will discuss financial programs that will allow you to take advantage of this increased performance as soon as possible. Identifying which peripheral devices can be retained and reused on the upgraded nodes will allow you to take advantage of your existing hardware investment. For those peripherals not supported we recommend maintaining a DN node to act a peripheral server. The ATR card is intended to be a migration aid while you move to a faster standard network for the future. You may wish to consider modifications to your existing network topology based on projected network traffic. This will prevent gateways from becoming bottleneck for transfer requests.